Skip to content

Comments

chore: update meetings.json and newsrooom_videos.json#5180

Merged
asyncapi-bot merged 1 commit intomasterfrom
update-meetings/5ffac5ca060d9c701a2c1fab2d7e74d032789617
Feb 19, 2026
Merged

chore: update meetings.json and newsrooom_videos.json#5180
asyncapi-bot merged 1 commit intomasterfrom
update-meetings/5ffac5ca060d9c701a2c1fab2d7e74d032789617

Conversation

@asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Feb 19, 2026

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • Chores
    • Extended the meetings list with a new Community Working Group Meeting entry.

@netlify
Copy link

netlify bot commented Feb 19, 2026

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 12fe9d4
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/69965fc2d7396d000833ca00
😎 Deploy Preview https://deploy-preview-5180--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 19, 2026

📝 Walkthrough

Walkthrough

This pull request adds a single new meeting entry to the meetings configuration file. A "Community WG Meeting" object with title, calendar link, URL, banner, and date fields is inserted into the existing meetings array in the JSON configuration.

Changes

Cohort / File(s) Summary
Configuration Update
config/meetings.json
Adds one new meeting entry ("Community WG Meeting") with associated metadata (calLink, url, banner, date) to the meetings array.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested labels

autoapproved, autoupdate

Suggested reviewers

  • derberg
  • akshatnema
  • anshgoyalevil
  • sambhavgupta0705
  • princerajpoot20
  • Mayaleeeee
  • asyncapi-bot-eve

Poem

🐰 A meeting is born in JSON's embrace,
With calendar links and a timestamp's grace,
Community gathers in config's fine place,
One object added, no logic to trace,
Configuration blooms in this data-filled space! 📅

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title mentions updating meetings.json and newsrooom_videos.json, but the raw summary only documents changes to config/meetings.json. The commit message indicates a third file (dashboard.json) was also changed, creating a mismatch between title and actual changeset. Update the PR title to accurately reflect all files modified in this changeset, or clarify which specific changes are the focus if the title should be more narrow.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch update-meetings/5ffac5ca060d9c701a2c1fab2d7e74d032789617

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@sonarqubecloud
Copy link

@asyncapi-bot
Copy link
Contributor Author

⚡️ Lighthouse report for the changes in this PR:

Category Score
🔴 Performance 43
🟢 Accessibility 98
🟢 Best practices 92
🟢 SEO 100
🔴 PWA 33

Lighthouse ran on https://deploy-preview-5180--asyncapi-website.netlify.app/

@codecov
Copy link

codecov bot commented Feb 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (5ffac5c) to head (12fe9d4).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #5180   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          796       796           
  Branches       146       146           
=========================================
  Hits           796       796           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@config/meetings.json`:
- Line 94: Update the "title" value for the meeting entry that currently reads
"Community WG Meeting" to include the "AsyncAPI" prefix so it matches the other
entries (i.e., change the "title" field value from "Community WG Meeting" to
"AsyncAPI Community WG Meeting"); locate the offending "title" key in the same
object that contains the current "Community WG Meeting" string and make the
string replacement there.

"date": "2026-02-17T15:00:00.000Z"
},
{
"title": "Community WG Meeting",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Title is missing the "AsyncAPI" prefix.

The new entry uses "Community WG Meeting" while all other equivalent entries in this file (Lines 3, 10, 73, 87) consistently use "AsyncAPI Community WG Meeting". This will likely render differently on the website compared to the prior entries of the same meeting series.

✏️ Proposed fix
-    "title": "Community WG Meeting",
+    "title": "AsyncAPI Community WG Meeting",
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"title": "Community WG Meeting",
"title": "AsyncAPI Community WG Meeting",
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@config/meetings.json` at line 94, Update the "title" value for the meeting
entry that currently reads "Community WG Meeting" to include the "AsyncAPI"
prefix so it matches the other entries (i.e., change the "title" field value
from "Community WG Meeting" to "AsyncAPI Community WG Meeting"); locate the
offending "title" key in the same object that contains the current "Community WG
Meeting" string and make the string replacement there.

@asyncapi-bot asyncapi-bot merged commit 52e5361 into master Feb 19, 2026
40 checks passed
@asyncapi-bot asyncapi-bot deleted the update-meetings/5ffac5ca060d9c701a2c1fab2d7e74d032789617 branch February 19, 2026 01:00
@github-project-automation github-project-automation bot moved this from To Be Triaged to Done in Website - Kanban Feb 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants